Add cpacs format checker - #1421

The failing wing W14_ChaDih has tip sections translated by exactly (0, 1, 1) and (0, 2, 2) — a perfect 45° dihedral. CTiglWingHelper::GetMajorDirection() picks the span axis by comparing accumulated |Y| vs |Z| with a plain >=, and for this wing those sums are mathematically equal, so the winner is decided by last-ULP rounding — which differs on arm64 (FMA contraction, Apple libm). The CI numbers prove it: 43.152389734005403 + 46.847610265994597 = 90.0 exactly — after SetSweep nudged the tip, the tie flipped the major axis and the dihedral was measured as its complement. Fix: a relative-tolerance tie-break (GreaterOrTied, 1e-8) in GetMajorDirection/GetDeepDirection (src/wing/CTiglWingHelper.cpp) so near-ties resolve deterministically to the conventional axis on every platform.

2. BSplineInterpolation.withKinksShield — over-strict test, fixed.
ArraysMatch defaults to exact ==, but the 0.5 parameter is derived arithmetic (tigl::Interpolate rescaling between kink params), which lands 1 ULP off on arm64. The test now uses InTolerance(1e-14).

3. SIGABRT in makeLoft.nacelleInverted — narrowed, needs one more CI run.
Three things the log tells us: (a) guideCurvePatches.nacelleInverted — same .brep inputs through MakePatches::Perform directly — passes on macOS, so the crash lives in the CTiglMakeLoft wrapper path (tolerance 1e-6 vs 1e-7, plus ConcatenateWire and CloseShape). That's why the MakePatches null-guard in your last commit couldn't fix it. (b) gtest catches C++ exceptions on POSIX, so a thrown CTiglError/Standard_Failure would show as a test failure, not an abort. (c) No libc++abi/assert message reached stderr — this is a silent abort (terminate-in-noexcept, heap check, or a direct abort()), which can't be pinpointed by reading code. So I added a temporary step to .github/workflows/build-test.yml that, when the macOS test job fails, reruns makeLoft.* under lldb --batch with thread backtrace all on crash — the next CI run will hand you the exact crash site.

Currently, the schema check is only included in the CI test on the
latest linux version in Debug mode. That should be sufficient to check.